home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20010306-20010921
/
000314_shifeux@hotmail.com_Tue Aug 14 16:51:58 EDT 2001.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
5KB
|
89 lines
Article: 12673 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!panix!howland.erols.net!news.maxwell.syr.edu!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: shifeux@hotmail.com (Shifeux)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit Scripts and Shell Scripts
Date: 14 Aug 2001 13:45:59 -0700
Organization: http://groups.google.com/
Lines: 70
Message-ID: <336f652d.0108141245.885b7f7@posting.google.com>
References: <336f652d.0108130841.43ce0ed5@posting.google.com> <336f652d.0108140545.1a1c8658@posting.google.com> <9lbdsm$35j$1@newsmaster.cc.columbia.edu> <336f652d.0108141029.39b5169f@posting.google.com> <9lbras$cfb$1@newsmaster.cc.columbia.edu>
NNTP-Posting-Host: 146.145.217.201
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 997821959 26297 127.0.0.1 (14 Aug 2001 20:45:59 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 14 Aug 2001 20:45:59 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:12673
I appreciate your help. The other scripts are all fine and each work
individually. They all have execute rights and are all spelled
correctly. I was able to reproduce the problem with a little test
kermit script which includes an echo followed by a run followed by
echos. It seems that when I include the run command it halts the
script and does not execute the run command or any commands after.
When I would add an echo (an echo through kermit everything was fine
and the script runs completly, but when i used the run command to send
the echo to the shell, again the script halted without executing the
run) We compiled the kermit on a seperate linux box and the scripts
worked fine. It seems the DG Unix box is the problem and possibly some
library or something? We are going to recompile the script and see
what happens. Again, I appreciate all your suggestions.
fdc@watsun.cc.columbia.edu (Frank da Cruz) wrote in message news:<9lbras$cfb$1@newsmaster.cc.columbia.edu>...
> In article <336f652d.0108141029.39b5169f@posting.google.com>,
> Shifeux <shifeux@hotmail.com> wrote:
> : I appologize for my 'jumbled' postings. I have several variations of
> : this script and I have ended up confusing the issue. The switch code
> : was just a different variation I tried when the IF and even XIF didn't
> : work for me. I plugged your piece of code into the script and I am
> : still getting the same result. The script crashes at the run <perl
> : script> command.
> :
> First of all, Kermit can run Perl or shell scripts if (a) they are
> executable, and (b) they begin with a line that specifies the script
> interpreter: sh, ksh, csh, bash, perl, kermit, or anything else.
>
> : What I am trying to do from a theory standpoint is
> : parse a directory listing on a remote machine to get a listing of the
> : files in a text file. This text file will be converted into a listing
> : and sent back to the remote system after I download the files in the
> : dir.
> :
> Of course you can do all this with Kermit just as well as with Perl.
>
> : I have a perl parse routine which does contain the
> : #!/usr/bin/perl in the first line
> :
> Is this the correct path for Perl? Does /usr/bin/perl exist?
>
> : (as a side note, my kermit script
> : does not contain a similar statement).
> :
> If it did, you could run it directly from the shell without having to
> start Kermit first. See:
>
> http://www.columbia.edu/kermit/ckscripts.html
>
> : The perl command will work
> : using the shell and using kermit, but when I use the 'run' command in
> : the script I have problems with the script itself. At the point of the
> : run command the script halts abruptly. It does not execute the perl
> : script at all which is indicated by no output file from the perl
> : script. I have commented out the run command line and added an echo
> : command and i see the echo and the script continues on as expected.
> : But when the run command is followed by the perl script name the
> : script ends abruptly. Am I missing something in the way kermit calls
> : upon the shell to execute the perl script?
> :
> Yes, you are missing something, but what you are missing is not obvious.
>
> The command that is not working is:
>
> run /kermit_scripts/xxxxxxx.pl
>
> The obvious question is: does the file /kermit_scripts/xxxxxxx.pl exist?
> Perhaps the initial slash shouldn't be there.
>
> - Frank